avformat/segment: Various segment muxer improvements by softworkz · Pull Request #96 · ffstaging/FFmpeg

softworkz · 2025-06-13T04:38:14Z

Includes

Two new options
- segment_write_temp
  Allows to write segments as temp files (.tmp) which are renamed on completion
- segment_limit
  Stop after n segments have been written
some minor changes (option contraints and formatting fixes)

Versions

V2

merge the documentation patch with the feature patch
segment_write_temp: use av_asprintf() directly instead of strlcatf() + av_strdup()
(as per review by Marton - thanks!)
removed logging patch

.

softworkz · 2025-06-13T05:52:50Z

/submit

ffmpeg-codebot · 2025-06-13T05:56:27Z

Submitted as [email protected]

To fetch this version into FETCH_HEAD:

git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-96/softworkz/submit_segment_muxer-v1

To fetch this version to local tag pr-ffstaging-96/softworkz/submit_segment_muxer-v1:

git fetch --no-tags https://github.com/ffstaging/FFmpeg tag pr-ffstaging-96/softworkz/submit_segment_muxer-v1

libavformat/segment.c

doc/muxers.texi

libavformat/segment.c

Allows to write segments as temp files (.tmp) which are renamed on completion. Signed-off-by: softworkz <[email protected]>

Example use case: Existing segments 0-30 and 70-99, 31-69 need to be created. This option allows to stop precisely after 69. Otherwise it would start overwriting segment 70 before stopping via 'q' or break signal. Signed-off-by: softworkz <[email protected]>

Use case is to keep early content out of the first segment when not starting from zero. Signed-off-by: softworkz <[email protected]>

Signed-off-by: softworkz <[email protected]>

softworkz · 2025-06-14T00:57:21Z

/submit

ffmpeg-codebot · 2025-06-14T01:00:57Z

Submitted as [email protected]

To fetch this version into FETCH_HEAD:

git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-96/softworkz/submit_segment_muxer-v2

To fetch this version to local tag pr-ffstaging-96/softworkz/submit_segment_muxer-v2:

git fetch --no-tags https://github.com/ffstaging/FFmpeg tag pr-ffstaging-96/softworkz/submit_segment_muxer-v2

ffmpeg-codebot · 2025-06-14T20:44:37Z

libavformat/segment.c

@@ -121,6 +121,9 @@ typedef struct SegmentContext {
    int   break_non_keyframes;


On the FFmpeg mailing list, Michael Niedermayer wrote (reply to this):

--===============8122640100284245730== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8AfFfcQwKZvQE1LI" Content-Disposition: inline --8AfFfcQwKZvQE1LI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 14, 2025 at 12:59:10AM +0000, softworkz wrote: > From: softworkz <[email protected]> >=20 > Signed-off-by: softworkz <[email protected]> > --- > libavformat/segment.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) should be ok thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. U= ser questions about the command line tools should be sent to the ffmpeg-user ML. And questions about how to use libav* should be sent to the libav-user ML. --8AfFfcQwKZvQE1LI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCaE3eQAAKCRBhHseHBAsP q266AJ9SI6yx8cvPZxKopJww1UchP4vodwCfYzQTYFxFp6OFaHU9o8q8Oh9eDtQ= =LqfM -----END PGP SIGNATURE----- --8AfFfcQwKZvQE1LI-- --===============8122640100284245730== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe". --===============8122640100284245730==--

softworkz force-pushed the submit_segment_muxer branch from 11124d5 to 88a8dc7 Compare June 13, 2025 05:20